-
Notifications
You must be signed in to change notification settings - Fork 612
update GPG key #1566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update GPG key #1566
Conversation
I'm seeing issues locally when trying to install:
I think that command should work? |
FWIW, issuing |
Hum, are you on RH7?
It is possible that the key for RH7 is the same than the one used for the pgdg-common. Before it was the same key for all versions.
Best regards,
Olivier
…________________________________
From: Jonathan Newman ***@***.***>
Sent: Thursday, January 4, 2024 7:03:41 PM
To: puppetlabs/puppetlabs-postgresql ***@***.***>
Cc: Vallejo Olivier ***@***.***>; Author ***@***.***>
Subject: Re: [puppetlabs/puppetlabs-postgresql] update GPG key (PR #1566)
FWIW, issuing rpm -Uvh https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm seems to fix things, which implies to me the keys aren't correct or incomplete?
—
Reply to this email directly, view it on GitHub<#1566 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKJTFFETTL6OAYSPQNYCH3LYM3VH3AVCNFSM6AAAAABBNFMBE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXGUZTOOJSG4>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Yes, well centos7
which seems to have nearly the identical content to the Additionally the yum.repos.d has this which implies the common key:
|
Ok I will adjust my branch to add a condition on the RH version, will do tomorrow.
Best regards,
Olivier
…________________________________
From: Jonathan Newman ***@***.***>
Sent: Thursday, January 4, 2024 7:32:26 PM
To: puppetlabs/puppetlabs-postgresql ***@***.***>
Cc: Vallejo Olivier ***@***.***>; Author ***@***.***>
Subject: Re: [puppetlabs/puppetlabs-postgresql] update GPG key (PR #1566)
Yes.
Running that command seems to install PGDG-RPM-GPG-KEY-RHEL7 in /etc/pki/rpm-gpg which has this content:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.22 (GNU/Linux)
mQGNBGWBsHEBDACzg9nBu9GXrquREAEVTObf6k3YIWagkv1qlX61dqQpyx8XT36A
+wx9qc7vk1mJoyzjq0gBH/C0ebaJntoCG/rv3j8DP4tQO+CApWN5XqrZJI+vYjRt
bJhrkxUt4fm8dozRykR9GdB05x35XVkzLsPVMqP6EqmBu9i2WgE30LlkPShzHyuf
P4W42zY4JVpKRK4CqLnWX3+PXY2tENYqkARK37j8r4klxIVku9UpE3W7XXIud9Nh
dVOtj0P8/t3mAHLgRjLqaGLVGz4k2b3phzDcG7sDvfwVXMPKDAVY5IymK4yTjeZU
6x3E63pNpQV4KfccHAKFJ++wOQmhfF5H+ViWTytIgyRMKn9eR+715nEZG8suRPSG
GnulJj9sUw6dONmPxCd6gCFQ0BAm/h7Bn8cODdPzJn6h/yMNs7SeH9yv8zlZvJdf
Sb5rTQLaFBaNP5yQ3rHb+gpDno7dwLxcx10qghPSz6TY96nCJNtrlj04P699UR4a
KIK2X6miJMwENE0AEQEAAbQ+UG9zdGdyZVNRTCBSUE0gUmVwb3NpdG9yeSA8cGdz
cWwtcGtnLXl1bUBsaXN0cy5wb3N0Z3Jlc3FsLm9yZz6JAbkEEwECACMFAmWBsHEC
GwMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRBk+s4Rc+O5B3MPC/4r2mTL
Oy7kuT48faVqDMovPsezJm//G/ur2dXMGYdr2QyzX1V6YXprtrY90bLt+mt/b/9C
pY0r5vDgI1uDkp5mX0tcCJJlAV8sDMC/r1a1rlh6KFxqRIOq5/hkPSkxHL4XVtdi
GvxgFcOj5vGWuBpmKaL+CeglBFzWFyPQV6+e+eJ4RG7MOOPHUUAODy58uDztSoyP
C8WLZR2vShTA5OZoyWdzwRkHeFMXWdcTw6wwff+sl942cwzkw5XotmkxS3Mpg4PI
IkGWeDvh2AoqjSIiLyAAB6vRhRjGwT+JLzQp0Yn9kfUQwMeCEOESO0mdnxd37WXq
+HvMY1I40J+OCl7XKE0kleWfsuv5/Hk+pHW4KxCHVtMKMpTzOT1Koq0dkx9H51p+
pubZZa5umPnhm9+0SkqotXaaBnxs+MBnQpu98TrJ0eOkpVRWqpkybXbrZKgx+oJN
xNctGxbgFRq3K7QMLGjor8vF5Mg6qTzxM5RwZ7QaT/Msjh8VyUZ6ch7kNcu5AY0E
ZYGwcQEMANOcY0IKEf4sMl3s2FHoZrxnjrX4cDdcS9NNYcYvDG1Y2BXiqEh6A5i1
ZpZQpUZitqXbFsU2GSEjC9IBKMklp0xTNt9lBC/WmlOFrwDgm0ufxMqiE77QlIyr
yVj+6XOMN8EotXF2a8ZxmqbYaG5L7eAqGsDda2ZYCqgwKQUkdXJ7QNq9ikQ31Toj
Qd0zzh1czDwDyj9bZCoPjZiCDZVmK5We87ZYWekDTIq9Wdh0teXzZrLb6UsFCMLO
zZDKlH4+5+zlYHyFvEjTxrrQs2YOkLLMcouRQKe/pR4DwKJvA9mLmofQWAHCH0uv
9SY08RXm+bqoNWwrCmCjdN775wUU9IsDaKXbdtybl6PprAQhwLceXysbr3HmorjV
nvJYujuwQMN6JUavKKLC3zJSDOnBlZBGfoR00QWG5mHSgRxXLNVtaAWAqxrNcofc
wOu0Rr9O89AAePHzvZKXCu6aeWeBfhgKAz+wIjh9VjNFjAFLLVP3nWOIPbjN+Blv
Wy/OXDWFXwARAQABiQGfBBgBAgAJBQJlgbBxAhsMAAoJEGT6zhFz47kHJHcL/A0m
Jme0ERyl2d9z9wfmH4/mJ3lEsSmYRk1y8cQLJ3yXSdD0iYFRDaiLdhuV6CZQQHee
ong6TpGTe1REmmKBSOD6zdCfCcAMsk+SKQHADJD9es0ZleQOpdcVRgnLKGcze2qx
JzS4+0OoNkPg0Wf5pdDlKi0nJIr/t1qLU7TVOWTcUaYhjnrHy8iCWVNvrmm9tPLJ
4dS3OCxdzuTApUQAC26Lo6T0SOIc7COyshuhZe90IK/cRMuDuvf+8TqWBOE2sMJ0
2WNS8In5xWItAfoepmFLSOeWbCHo/yzuVFFI7Oo4DJ5cvKJ+Vo3iAWl8RPsN6iKE
Ocmphnc2clno8y4lSc4NckEbL+teZZyww12kHph5NUDReITO4H/4XGEpq4PATT6P
9aMDQQVK4GpmIZ6pLn+yYOV/ZLkHIcJUBVPjLtds5FOsVEpX4JaMowzk4jT6lp/F
7inS2V/87DcrYMl+NcBm09BZ6M4X1OYEumq7qXKtScmHAfp2yG2A1lJ5RtXrSQ==
=fPP0
-----END PGP PUBLIC KEY BLOCK-----
which seems to have nearly the identical content to the common key in this PR.
Additionally the yum.repos.d has this which implies the common key:
[pgdg-common]
name=PostgreSQL common RPMs $releasever - $basearch
baseurl=https://download.postgresql.org/pub/repos/yum/common/redhat/rhel-$releasever-$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG-common
repo_gpgcheck=1
—
Reply to this email directly, view it on GitHub<#1566 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKJTFFHFLEWYSNGNDHEM7MDYM3YTVAVCNFSM6AAAAABBNFMBE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXGU3TIMRWGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Additionally tested on AlmaLinux 8 and redhat 8 and they have issues finding the packages:
|
Issuing |
There is code to manage the DNF module: puppetlabs-postgresql/manifests/globals.pp Lines 280 to 284 in 0b610d1
However, I didn't consider ensuring the DNF module is absent so you can use the package repo. Perhaps the logic needs to be enhanced that if you enable |
After checking on CentOS7, Almalinux8 and Almalinux9 it indeed seems that the GPG key is different on RH7 than the others. I have pushed a new change, with his version I am able to properly install PostgreSQL on both CentOS7 and Almalinux9. |
Confirmed working on centos7. Works on almalinux8 and redhat 8 with the
Seems like that should be a separate issue? |
imho, module should provide a parameter to override location of the key, this way module users can easily address it via hiera in the future |
Thanks @vaol for raising the PR and @jonathannewman & @donoghuc for validating and review. I was looking at pipeline failures for CentOS, AlmaLinux and Rocky, the rerun doesn't work as expected so tried locally (CentOS & AlmaLinux) and works fine but here on github actions there are not showing much details. Checking further. |
Looks like while running test for multi instance postgresql (https://github.com/puppetlabs/puppetlabs-postgresql/blob/main/spec/acceptance/server_instance_spec.rb#L18-L21), the spec trying to stop main postgres service and thats where it hags and keep waiting for service to stop.
Process
|
@vaol can you please rebase the PR? |
Hello, sure, I just did. Let me know if anything else. |
@Ramesh7 is there a new GH issue or puppet ticket tracking this work? #1566 (comment) |
Summary
Provide a detailed description of all the changes present in this pull request.
Additional Context
Add any additional context about the problem here.
Related Issues (if any)
Mention any related issues or pull requests.
Checklist
puppet apply
)